
(Note: The origin of this information may be internal or external to Novell. 
Novell makes every effort within its means to verify this information. 
However, the information provided in this document is FOR YOUR INFORMATION
only.  Novell makes no explicit or implied claims to the validity of this
information.)

          TITLE:     Installing Windows And RPRINTER On Same workstation.
   DOCUMENT ID#:     FYI.P.5272
           DATE:     07JAN92
        PRODUCT:     NetWare
PRODUCT VERSION:     All versions
     SUPERSEDES:     NA

        SYMPTOM:     NA

ISSUE/PROBLEM

     The following are suggestions for installing Windows and Rprinter on the
same workstations:

     *     SETUP /I.

     Undocumented switch that ignores checking the hardware at the time of
installing Windows.  It needs to be mentioned that leaving the /i out can
also be helpful in some cases.

     *     PUT WINDOWS ON A LOCAL DRIVE.

     Windows is faster on a local drive than from a Network drive.  Also
sometimes you can work in real mode from the Network but not in enhanced
mode.

     *     USE HIMEM.SYS FOR THE MEMORY MANAGER.

     Windows has been successfully installed with Qemm386.sys and Emm386.sys
from Quarterdeck and DR DOS 6.0 respectively with Windows on local and
Network drives, however, tweaking these two memory managers can be a
struggle.

     *     MAY NEED TO USE HIMEM.SYS /M:1 IN THE CONFIG.SYS.

     In the Readme.txt in the Windows subdirectory, it explains the use of
this switch.  It is used to make sure Windows sees a 100% IBM compatible
BIOS.  

     Other options include:
  
          1  at               ; IBM AT or 100% compatible.
          2  ps2              ; IBM PS/2
          3  ptlcascade       ; Phoenix Cascade BIOS
          4  hpvectra         ; HP Vectra (A & A+)
          5  att6300plus      ; AT&T 6300 Plus
          6  acer1100         ; Acer 1100
          7  toshiba          ; Toshiba 1600 & 1200XE
          8  wyse             ; Wyse 12.5 Mhz 286 

     If HIMEM does not work properly, trying a different method may be
successful.   Specify the switch for your computer type on the
device=HIMEM.SYS line in your CONFIG.SYS file. Computer type corresponds to
either the number or the name of your computer from the table.

     For example the following lines are equivalent:

          device=c:\himem.sys /M:ps2
          device=c:\himem.sys /M:2

     *     GET THE LATEST NETX FROM DOSUP4.ZIP.

     Always get the latest Shells found in NOVLIB lib 05. 

     *     GET THE NOVELL WORKSTATION UTILITIES FOR WINDOWS FOUND IN
WINUP4.ZIP.   
     These utilities simplify the printing/capture environment in Windows.
They are also found in NOVLIB lib 05.  At the time of installing the
utilities, some changes are made to the system.ini of that workstation. 
These changes include drivers such as VPICDA.386 which can help interrupt
conflicts associated with IRQ's 2 and 9.

     *     TRY TO EXCLUDE DIFFICULT ADDRESSES SUCH AS VIDEO RAM AND NIC I/O
WITHIN THE SYSTEM.INI FILE.   

     This is documented on page 549 of the Windows User Guide.  The following
is an example:

          1.     Find the [386en] section of the System.ini file using a text
editor.

          2.     Add the line: EMMExclude=A000-DFFF (or address of problem
areas).

          3.     Save the file and reenter Windows.

     *     MAY NEED TO AVOID IRQ'S 2, 9, OR 3 WHEN INSTALLING THE NIC IN THE
WORKSTATION.   

     IRQ 3 may be a problem if there is a com3 in the workstation and
sometimes  experience interrupt problems even if com3 is not enabled.

     *     ALWAYS EXECUTE RPRINTER.EXE BEFORE GOING INTO WINDOWS.   

     The syntax from the dos prompt is: rprinter print_server_name
printer_number

     *     PUT SPX ABORT TIMEOUT=1000 IN THE SHELL.CFG FILE FOUND ON THE
WORKSTATION.  This often helps when the printer loses connection as seen at
the Print Server's status screen.

     *     I/O CONFLICTS WITH THE NIC'S CAN CAUSE PROBLEMS.

     On an AST 386sx workstation using an NE2000 set at base I/O of 360 would
run fine with Rprinter and Windows in enhance mode until the job was printed
to the queue serviced by the Rprinter.  At that time the workstation would
hang and the status at the Print Server status screen would show Rprinter not
connected.  If we used IRQ 3 and 5 at I/O address of 300 or 340 it worked
fine all the time.

     *     AVOID OTHER TSR'S AT THE WORKSTATION USING BOTH RPRINTER AND
WINDOWS.

     *     WINDOWS REQUIRES 2 MEG OF EXTENDED RAM TO RUN IN ENHANCED MODE.

     *     WINDOWS REQUIRES THE HMA TO RUN IN ENHANCED MODE.

     This means that the 64K byte segment above the one meg boundary (address
FFFFF) has to be unused.  Some applications such as our XMSNETX.COM loads
into the HMA (Hi Memory Area).  Some memory managers such as EMM386.sys from
DRI, load the DR DOS 6.0 kernel into this same HMA, once again not allowing
Windows to run in enhanced mode.  MSDOS 5.0 kernel can have the same effect.

     *     There are so many combinations regarding hardware, memory manager
settings, and how users load programs into upper memory, it is more or less
a trial and error situation when using windows and rprinter. There is not a
sure method of installing windows and rprinter on the same workstation and
making them work successfully all the time.

From: Kristin Vane And Kimo Lewis

 